Embedded on-board diagnostic (obd) device for a vehicle

ABSTRACT

Embodiments described herein provide various examples of a low cost, low power, fully automated, unobtrusive, and vehicle-independent radio frequency (RF) communication device to be plugged into a standard on-board diagnostic (OBD) port inside a vehicle to access OBD diagnostic data. According to one aspect, an OBD device for a vehicle is disclosed. This OBD device includes: an OBD adapter configured to be plugged into an OBD port of a vehicle and a first RFID module electrically coupled to the OBD adapter. The first RFID module is further configured to receive OBD data of a vehicle from an associated OBD port via the OBD adapter and communicate at least a portion of the received OBD data to a first RFID reader when the first RFID module is queried by the first RFID reader.

PRIORITY CLAIM AND RELATED PATENT APPLICATIONS

This patent document claims benefit of priority under 35 U.S.C. 119(e)to U.S. Provisional Patent Application No. 62/218,518 entitled “ON-BOARDDEVICE” and filed on Sep. 14, 2015. The disclosures of the aboveapplication are incorporated by reference in their entirety as a part ofthis document.

The present application is related to U.S. Pat. No. 8,344,890, issued onJan. 1 2013, U.S. Pat. No. 9,007,215, issued on Apr. 14, 2015, U.S. Pat.No. 7,081,819, issued on Jul. 25, 2006, U.S. Pat. No. 7,671,746, issuedon Mar. 2, 2010, U.S. Pat. No. 8,237,568, issued on Aug. 7, 2012, U.S.Pat. No. 8,325,044, issued on Dec. 4, 2012, U.S. Pat. No. 8,004,410,issued on Aug. 23, 2011, Reissued U.S. Pat. Nos. RE 43,355, issued onMay 8, 2012 and RE 44,691, issued on Jan. 7, 2014, U.S. patentapplication Ser. No. 14/459,299, filed on Aug. 13, 2014, now U.S. Pat.No. 9,355,398, issued on May 31 2016 and U.S. patent application Ser.No. 14/250,356, filed on Apr. 10, 2014, U.S. Pat. No. 7,034,688, issuedon Apr. 25, 2006 and U.S. Pat. No. 7,463,154, issued on Dec. 9, 2008,all which are hereby incorporated by reference in their entirety.

BACKGROUND

1. Technical Field

The various embodiments described herein are related to wirelessdevices, and more particularly to an on-board diagnostic (OBD) devicewith wireless capability which may be used inside a vehicle.

2. Related Art

Since 1996, new cars sold in the United States have included an On-BoardDiagnostic (OBD) port/connector which is designed to allow a standardizeway to access a vehicle's diagnostic information. Various types ofcommunication devices and gadgets have been designed or adapted toaccess vehicle's internal sensor data via the OBD port using eitherwired or wireless connections to the OBD port. These devices coupled tothe OBD ports facilitate vehicle self-diagnostics and self-reportcapabilities. In addition to the convenience of easily understanding theroot causes of vehicle's warning signals, such as a lit check-enginelight, these devices can turn the routine diagnostic information into aresource to enable a wide range of useful applications. For example, theobtained diagnostic information can be turned into driving habit data toallow an insurance company to adjust a drive's insurance rate based onhow a person drives. As another example, the obtained diagnosticinformation can be displayed in real-time to the driver and when coupledwith the GPS data, allowing the driver to monitor and visualize thesophisticated performance parameters of the vehicle traveling in aparticular route.

Conventionally, a user device, such as a diagnostic tool or a user'ssmartphone can be configured to communicate with the OBD port through awireless connection, such as a cellular data connection (e.g., in theM2M solution), Wi-Fi, or Bluetooth™. However, each of the above wirelessconnection technologies is associated with high power consumption andhigh cost.

SUMMARY

Embodiments described herein provide various examples of a low cost, lowpower, fully automated, unobtrusive, and vehicle-independent radiofrequency (RF) communication device to be plugged into a standard OBDport inside a vehicle to access OBD diagnostic data of the vehicle. Thisdevice is also referred to as an “on-board diagnostic (OBD) device.” Invarious embodiments, the disclosed OBD device can be embedded into anyvehicle including a standard OBD port/connector, and be configured toaccess OBD diagnostic data through the standard OBD port/connector. Invarious embodiments, the disclosed embedded OBD device is configured tocommunicate with a radio frequency identification (RFID) readerinfrastructure, including providing vehicle's OBD data to RFID readersof the RFID reader infrastructure, which can include both stationary andhandheld RFID readers.

According to one aspect, an on-board diagnostic (OBD) device for avehicle is disclosed. This OBD device includes: an OBD adapterconfigured to be plugged into an OBD port of a vehicle and a first RFIDmodule electrically coupled to the OBD adapter. The first RFID module isfurther configured to: receive OBD data of a vehicle from an associatedOBD port via the OBD adapter; and communicate at least a portion of thereceived OBD data to a first RFID reader when the first RFID module isqueried by the first RFID reader.

In some embodiments, the first RFID module is an ultra-high frequency(UHF) RFID module configured to communicate with the first RFID readerusing an UHF frequency band. The first RFID reader can be installed at afirst location by the roadside, and in this configuration, the firstRFID module can communicate with the first RFID reader when a vehiclecarrying the OBD device passes through the first location. The firstRFID reader can also be installed at a second location in a gantry abovethe ground, and in this configuration, the first RFID module cancommunicate with the first RFID reader when a vehicle carrying the OBDdevice passes under the second location. However, the first RFID readercan also be a handheld RFID reader.

In some embodiments, the OBD adapter of the OBD device is configured asa pass-through connector such that when the OBD adapter is plugged intoan OBD port of a vehicle, the OBD adapter allows another ODB device toaccess the OBD port without obstruction. This can be achieved byconfiguring the pass-through connector with a pass-through port that issubstantially identical to the OBD port, so that when the OBD adapter isplugged into the OBD port, another ODB device can continue to access theOBD port by plugging into the pass-through port.

In some embodiments, the first RFID module is configured as a passiveRFID module which functions without requiring power from either avehicle or the OBD device. This property allows the first RFID module tocommunicate with the first RFID reader when the OBD device is switchedoff or non-functional.

In some embodiments, the OBD device further includes a second RFIDmodule electrically coupled to the OBD adapter. This second RFID moduleis further configured to: receive OBD data of a vehicle from anassociated OBD port via the OBD adapter; and communicate at least aportion of the received OBD data to a second RFID reader when the secondRFID module is queried by the second RFID reader. In some embodiments,the second RFID module is a high frequency (HF) RFID module configuredto communicate with the second RFID reader using a HF frequency band.For example, the second RFID module can be configured to communicatewith a near-field communication (NFC)-enabled device.

In some embodiments, the second RFID module is configured as a passiveRFID module which functions without requiring power from either avehicle or the OBD device. This property allows the second RFID moduleto communicate with the second RFID reader when the OBD device isswitched off or non-functional.

In some embodiments, the OBD device also includes a microprocessorcoupled between the OBD adapter and the first RFID module and configuredto process the received OBD data via the OBD adapter. In someembodiments, the microprocessor is coupled to the first RFID modulethrough an I²C control bus.

In some embodiments, the disclosed OBD device is configured to operatewithout requiring a network connection, a data service, or a pairing toanother networked device.

In a further aspect, a process for providing OBD data of a vehicle to anRFID reader is disclosed. This process starts by receiving a query forOBD data from an RFID reader. Next, the process uses an UHF RFID moduleelectrically coupled to an OBD port of the vehicle to receive thecurrent OBD data of the vehicle. The process subsequently uses the UHFRFID module to transmit the current OBD data to the RFID reader.

In yet another aspect, a process for providing OBD data of a vehicle toan RFID reader is disclosed. This process starts by querying, from anOBD port of the vehicle, OBD data of the vehicle using an OBD adapter ofan OBD device coupled with the OBD port. The process subsequently storesat least a portion of the received OBD data into a memory of the OBDdevice. Next, the process receives a query from an RFID reader for theOBD data of the vehicle. The process then uses an RFID module of the OBDdevice to transmit at least a portion of the stored OBD data to the RFIDreader. In some embodiments, querying the OBD data and storing the atleast a portion of the received OBD data into the memory of the OBDdevice are performed periodically at a predetermined time interval.

Other features and advantages of the present inventive concept should beapparent from the following description which illustrates by way ofexample aspects of the present inventive concept.

BRIEF DESCRIPTION OF THE DRAWINGS

The structure and operation of the present disclosure will be understoodfrom a review of the following detailed description and the accompanyingdrawings in which like reference numerals refer to like parts and inwhich:

FIG. 1 shows a diagram illustrating an exemplary RFID system inaccordance with one embodiment described herein.

FIG. 2 shows a schematic diagram of an exemplary embedded OBD device inaccordance with one embodiment described herein.

FIG. 3 presents a photographic image of a prototype OBD device inaccordance with one embodiment described herein.

FIG. 4 shows a schematic diagram of an exemplary OBD system which usesthe embedded OBD device described in FIG. 2 to query and transmit OBDdata in accordance with one embodiment described herein.

FIG. 5 illustrates a highly efficient rental car return processimplemented based on communicating with a disclosed OBD device pluggedinto the OBD port of a rental vehicle in accordance with one embodimentdescribed herein.

DETAILED DESCRIPTION

While certain embodiments are described, these embodiments are presentedby way of example only, and are not intended to limit the scope ofprotection. The methods and systems described herein can be embodied ina variety of other forms. Furthermore, various omissions, substitutions,and changes in the form of the example methods and systems describedherein can be made without departing from the scope of protection.

Embodiments described herein provide various examples of a low cost, lowpower, fully automated, unobtrusive, and vehicle-independent radiofrequency (RF) communication device to be plugged into a standard OBDport inside a vehicle to access OBD diagnostic data of the vehicle. Thisdevice is also referred to as an “on-board diagnostic (OBD) device.” Invarious embodiments, the disclosed OBD device can be embedded into anyvehicle including a standard OBD port/connector, and be configured toaccess OBD diagnostic data through the standard OBD port/connector. Insome embodiments, the disclosed embedded OBD device is configured tocommunicate with a radio frequency identification (RFID) readerinfrastructure, including providing vehicle's OBD data to RFID readersof the RFID reader infrastructure, which can include both stationary andhandheld RFID readers.

According to one aspect, an on-board diagnostic (OBD) device for avehicle is disclosed. This OBD device includes: an OBD adapterconfigured to be plugged into an OBD port of a vehicle and a first RFIDmodule electrically coupled to the OBD adapter. The first RFID module isfurther configured to: receive OBD data of a vehicle from an associatedOBD port via the OBD adapter, and communicate at least a portion of thereceived OBD data to a first RFID reader when the first RFID module isqueried by the first RFID reader.

In a further aspect, a process for providing OBD data of a vehicle to anRFID reader is disclosed. This process starts by receiving a query forOBD data from an RFID reader. Next, the process uses an UHF RFID moduleelectrically coupled to an OBD port of the vehicle to receive thecurrent OBD data of the vehicle. The process subsequently uses the UHFRFID module to transmit the current OBD data to the RFID reader.

In yet another aspect, a process for providing OBD data of a vehicle toan RFID reader is disclosed. This process starts by querying, from anOBD port of the vehicle, OBD data of the vehicle using an OBD adapter ofan OBD device coupled with the OBD port. The process subsequently storesat least a portion of the received OBD data into a memory of the OBDdevice. Next, the process receives a query from an RFID reader for theOBD data of the vehicle. The process then uses an RFID module of the OBDdevice to transmit at least a portion of the stored OBD data to the RFIDreader. In some embodiments, querying the OBD data and storing the atleast a portion of the received OBD data into the memory of the OBDdevice are performed periodically at a predetermined time interval

FIG. 1 shows a diagram illustrating an exemplary RFID system 100 inaccordance with one embodiment described herein. In system 100, RFIDinterrogator/reader 102 communicates with one or more RFID tags 110.Data can be exchanged between interrogator/reader 102 and RFID tag 110via radio transmit signal 108 and radio receive signal 112. RFIDinterrogator/reader 102 comprises RF transceiver 104, which containstransmitter and receiver electronics, and antenna 106, which areconfigured to generate and receive radio transit signal 108 and radioreceive signal 112, respectively. Exchange of data can be accomplishedvia electromagnetic or electrostatic coupling in the RF spectrum incombination with various modulation and encoding schemes.

RFID tag 110 is a transponder that can be attached to an object ofinterest and act as an information storage mechanism. In manyapplications, the use of passive RFID tags is desirable, because theyhave a virtually unlimited operational lifetime and can be smaller,lighter, and cheaper than active RFID tags that contain an internalpower source, e.g. battery. Passive RFID tags power themselves byrectifying the RF signal emitted by the RF scanner. Consequently, therange of transmit signal 108 determines the operational range of RFIDtag 110. RFID tag 110 can includes a memory 120 to store tag informationand/or application-specific data. Data stored on memory 120 can be readby RFID interrogator/reader 102 through radio transit signal 108.Moreover, memory 120 can be written and/or updated by RFIDinterrogator/reader 102 with data embedded in radio transit signal 108.

RF transceiver 104 transmits RF signals to RFID tag 110, and receives RFsignals from RFID tag 110, via antenna 106. The data in transmit signal108 and receive signal 112 can be contained in one or more bits for thepurpose of providing identification and other information relevant tothe particular RFID tag application. In some embodiments, RFID tag 110and RFID interrogator/reader 102 are not in a fixed configuration, forexample, RFID tag 110 can be installed on a vehicle while RFIDinterrogator/reader 102 is installed near a toll booth and. In theseembodiments, when RFID tag 110 passes within the range of the radiofrequency magnetic field emitted by antenna 106 of RFIDinterrogator/reader 102, RFID tag 110 is excited and transmits data backto RF interrogator/reader 102. In other embodiments, RFID tag 110 andRFID interrogator/reader 102 are in a fixed configuration, for example,both RFID tag 110 and RFID interrogator/reader 102 can be installed onthe same vehicle. In these embodiments, RFID tag 110 can be excited andtransmit data back to RF interrogator/reader 102 when RFIDinterrogator/reader 102 is activated and begins to emit radio transitsignal 108 through antenna 106. Alternatively, RFID tag 110 can beexcited and allow data to be written into memory 120 when RFIDinterrogator/reader 102 is activated and begins to transmit dataembedded in radio transit signal 108 through antenna 106.

In some implementations, in response to radio transit signal 108transmitted by RF interrogator/reader 102 to access data stored onmemory 120 of RFID tag 110, a change in the impedance of RFID tag 110can be used to signal the data to RF interrogator/reader 102 via receivesignal 112. The impedance change in RFID tag 110 can be caused byproducing a short circuit across the tag's antenna connections (notshown) in bursts of very short duration. RF transceiver 104 senses theimpedance change as a change in the level of reflected or backscatteredenergy arriving at antenna 106.

Digital electronics 114, which can comprise a microprocessor with RAM,performs decoding and reading of receive signal 112. Similarly, digitalelectronics 114 performs the coding of transmit signal 108. Thus, RFinterrogator/reader 102 facilitates the reading or writing of data toRFID tags, e.g. RFID tag 110 that are within range of the RF fieldemitted by antenna 104. Together, RF transceiver 104 and digitalelectronics 114 comprise RF interrogator/reader 102. Finally, digitalelectronics 114 and can be interfaced with an integral display and/orprovide a parallel or serial communications interface to a host computeror industrial controller, e.g. host computer 116.

In some embodiments, one or more RFID transponders (e.g., RFID tag 110described with respect to FIG. 1) can be embedded in an OBD adaptorconfigured to be plugged into an OBD port/connector of a vehicle to forman embedded OBD device for a vehicle. In some embodiments, this embeddedOBD device can be configured to access OBD data by querying an OBD port,such as a standard OBD-II of a vehicle, record at least a portion of thequeried OBD data in a memory of the RFID transponder or a separate ICchip embedded in the OBD device, and transmit at least a portion of thequeried OBD data to an RFID reader when the OBD device is queried by theRFID reader. In some embodiments, the OBD data queried by the OBD devicewhich can then be transmitted to the RFID readers can include vehicle'sVIN number, mileage, fuel level, tire pressure monitoring system (TPMS)threshold, and various diagnostic trouble codes.

FIG. 2 shows a schematic diagram of an exemplary embedded OBD device 200in accordance with one embodiment described herein. Embedded OBD device200 can include an adapter 202. In various embodiments, adapter 202includes a male/female connector to be plugged into a standardfemale/male OBD port, such as an OBD-II port. In some embodiments,adapter 202 is configured as a “pass-through connector” such that whenOBD device 200 is plugged into a standard OBD port of a vehicle, adapter202 allows another ODB device to continue to access the standard OBDport without obstruction. In some embodiments, adapter 202 is configuredas the pass-through connector by including a outward-facing pass-throughport/connector that is substantially identical to the original OBDport/connector, so that another ODB device can be plugged into theoutward-facing port/connector of adapter 202 to continue to access thestandard OBD port.

In some embodiments, OBD device 200 can include an ultra high frequency(UHF) Radio Frequency Identification (RFID) module 204 configured toallow OBD device 200 to communicate with RFID readers positioned from amid-distance to a long distance from the location of OBD device 200 andan associated OBD port. For example, when OBD device 200 is embedded ina vehicle by plugging into the standard OBD port, UHF RFID module 204 isconfigured to communicate with RFID readers installed on the roadsidewhen the vehicle passes through the RFID readers, or with RFID readersinstalled in a gantry under which the vehicle drives through. In someembodiments, UHF RFID module 204 can include an UHF integrated circuit(IC) chip and an UHF antenna/loop, wherein the UHF IC chip can include amemory and other circuits. Furthermore, the memory component of the UHFIC chip within UHF RFID module 204 can store data including, but are notlimited to, parameters of OBD device 200, user and/or vehicle identitydata (e.g., a VIN number), as well as OBD diagnostic data obtained viathe OBD port. In some embodiments, the memory of UHF RFID module 204includes a non-volatile memory.

UHF RFID module 204 can be configured as a passive module withoutrequiring power from either the vehicle where OBD device 200 isinstalled or OBD device 200 itself. This feature can be useful when thevehicle is not in operation or when OBD device 200 is switched off ornon-functional. In these scenarios, a passive UHF RFID module 204 canstill be queries by an RFID reader within an UHF communication range ofOBD device 200. However, UHF RFID module 204 can also be configured asan active or battery-assisted passive module without departing from thescope of present disclosure. In some embodiments, the communicationbetween UHF RFID module 204 and the RFID readers is encrypted for secureand authorized communication.

In some embodiments, OBD device 200 can also include a short range highfrequency (HF) RFID module 206 configured to allow OBD device 200 tocommunicate with a mobile device such as a smartphone or a tablet usingthe short range RF module. In particular embodiments, HF RFID module 206includes a near field communication (NFC) RFID tag configured tocommunicate with a user's NFC-enabled mobile device. For example, whenOBD device 200 is installed on a vehicle, an NFC RFID module 206 isconfigured to communicate with driver's smartphone or the on-boardcomputer of the vehicle. In some embodiments, HF RFID module 206 caninclude an HF IC chip and an HF antenna/loop, wherein the IC chip caninclude a memory and other circuits. Furthermore, the memory componentof the IC chip within HF RFID module 206 can store data including, butare not limited to, parameters of OBD device 200, user and/or vehicleidentity data (e.g., a VIN number), as well as OBD diagnostic dataobtained via the OBD port. In some embodiments, the memory of HF RFIDmodule 206 includes a non-volatile memory.

HF RFID module 204 can be configured as a passive module withoutrequiring power from either the vehicle where OBD device 200 isinstalled or OBD device 200 itself. This feature can be useful when thevehicle is not in operation or when OBD device 200 is switched off ornon-functional. In these scenarios, a passive NFC RFID module 206 canstill be queries by a user's NFC-enabled mobile device within a NFCcommunication range of OBD device 200. However, HF RFID module 206 canalso be configured as an active or battery-assisted passive modulewithout departing from the scope of present disclosure. In someembodiments, HF RFID module 206 can also be configured as a Bluetooth™module or a Wi-Fi module.

Although the embodiment of OBD device 200 in FIG. 2 shows both an UHFRFID module 204 and an HF RFID module 206, other embodiments of thedisclosed OBD device 200 can include just UHF RFID module 204 butwithout HF RFID module 206. In these embodiments, the exemplary OBDdevice 200 is not capable of communicating with a HF RFID reader or anNFC device. In other embodiments, an exemplary OBD device 200 caninclude one or more UHF RFID modules and one or more HF RFID modules.

OBD device 200 can also include a microprocessor 208 coupled betweenadapter 202 and UHF RFID module 204, and between adapter 202 and HF RFIDmodule 206. Microprocessor 208 of the present disclosure can be anyintegrated circuit (IC) that is designed to execute instructions byperforming arithmetic, logical, control and input/output (I/O)operations specified by algorithms. In some embodiments, microprocessor208 is an application specific integrated circuit (ASIC) that isdesigned for a particular use rather than for general purpose use. Insome embodiments, microprocessor 208 is configured to process the OBDdiagnostic data received through adapter 202 and determine root causesof fault codes transmitted by the OBD port. In various embodiments,microprocessor 208 can be connected to the IC chip in UHF RFID module204 and/or the IC chip in HF RFID module 206 through I²C control buses.In some embodiments, each of UHF RFID module 204, HF RFID module 206,and microprocessor 208 is a self-contained module which are separatelymanufactured and subsequently assembled into a single package. In otherembodiments, UHF RFID module 204, HF RFID module 206, and microprocessor208 are manufactured onto the same PCB.

Note that microprocessor 208 can receive power directly from one or morepins of adapter 202. However, microprocessor 208 can also receive powerfrom a battery unit (not shown) integrated with OBD device 200. However,as mentioned above, each of the UHF RFID module 204 and HF RFID module206 can be configured to be power-independent and continues to functionwhen OBD device 200 is switched off or non-functional.

The disclosed embedded OBD device 200 is small (e.g., having a formfactor comparable to the standard OBD port), unobtrusive (e.g., whenconfigured in a pass-through configuration, keeps OBD port available),and invisible to the customers. In various embodiments, the disclosedOBD device 200 can be embedded into any vehicle including a standard OBDII port/connector or a variation of the standard OBD II port/connector,and be configured to access OBD diagnostic data through the standard OBDpins. Furthermore, the disclosed OBD device 200 can have a lowinstallation cost because the installation process can be as easy asfinding the vehicle's OBD port and plugging in the device. Because ofusing the standard interface and data protocol, the disclosed embeddedOBD device 200 can also be transferred from one vehicle to the next bysimply unplugging the device from one vehicle and plugging it into thenext vehicle. In various embodiments, the disclosed embedded OBD device200 is configured to communicate with an RFID reader infrastructure,which can include both stationary and handheld RFID readers.

FIG. 3 presents a photographic image of a prototype OBD device 300 inaccordance with one embodiment described herein. As can be seen in FIG.3, prototype OBD device 300 includes an OBD adapter 302 which furtherincludes a male connector 304 and a house 306 containing a PCB, amicrocontroller and RFID chips (not shown). OBD device 300 also includesan antenna module 308 for the RFID module which is connected to adapter302 via a cable 310. The particular configuration of OBD device 300 canfacilitate performing read performance testing of OBD device 300 basedon the position and location of OBD device 300 within the vehicle. Theparticular configuration of OBD device 300 can also facilitate testingof antenna module 308 in different shapes and sizes. Moreover, OBDadapter 302 of OBD device 300 can be an off-the-shelf component capableof accommodating a PCB for integrating the microcontroller and RFIDchips. In some embodiments, the microcontroller inside adapter 302stores an OBD device firmware configured to control desired devicefunctionalities. For example, one of such device functionalitiescontrolled by the firmware includes displaying the collected OBD data ina particular format.

FIG. 4 shows a schematic diagram of an exemplary OBD system 400 whichuses the embedded OBD device 200 described in FIG. 2 to query andtransmit OBD data in accordance with one embodiment described herein. Inthe system of FIG. 4, OBD device 200 is plugged into the standard OBDport (not shown) of vehicle 402 at a location within or behind dashboard404. In other vehicles however, the standard OBD port is located at alocation outside of the area of the dashboard. As mentioned above,adapter 202 within OBD device 200 can be configured as a pass-throughconnector to include an interface that is substantially identical to thestandard OBD port/connector. Hence, when OBD device 200 is plugged intothe OBD port of vehicle 402, this pass-through connector still allowsother ODB devices to continue to access the OBD port withoutobstruction.

UHF RFID module 204 within OBD device 200 can communicate with aplurality of RFID readers 408 which can include readers installed by theroadside or handheld readers. In some embodiments, RFID readers 408include both roadside readers and handheld readers. When RFID readers408 are configured as roadside readers, RFID readers 408 can beinstalled as high as 200 feet if UHF RFID module 204 within OBD device200 is configured in an active mode. RFID readers 408 can be connectedto one or more back-end servers 412 via a network 410, which can beconfigured as one of the many network systems such as General PacketRadio Service (GPRS), Wi-Fi, or Ethernet. RFID readers 408 can streamOBD data received from OBD device 400 to back-end servers 412, which runvarious user applications 414A and 414B.

In some embodiments, UHF RFID module 204 within OBD device 200 caninclude two operations modes: a pass-through mode and a continuouscollect mode. More specifically, in the pass-through mode, relevant OBDdata received from the standard OBD port is transmitted to an RFIDreader at the moment when OBD device 200 is queried by an RFID reader408. In contrast, in the continuous mode, OBD device 200 queries thestandard OBD port for relevant OBD data and subsequently stores thequery results within a memory of OBD device 200. In some embodiments,the OBD data can include vehicle's VIN number, mileage, fuel level, tirepressure monitoring system (TPMS) threshold, and various diagnostictrouble codes. The query can be performed periodically at apredetermined time interval, e.g., every minute. Next, when OBD device200 is queried by an RFID reader 408, OBD device 200 returns the OBDdata stored in the memory to the RFID reader.

HF RFID module 206 within OBD device 200 can communicate with a userdevice such as a mobile phone 416 positioned inside vehicle 402. When HFRFID module 206 is configured as an NFC RFID module, HF RFID module 206can communicate with an NFC interface of mobile phone 416. Mobile phone416 can be connected to back-end servers 412 via a cellular network 418and stream OBD data received from OBD device 200 to back-end servers 412via cellular network 418.

One or more of the RFID modules within OBD device 200 can also interfacewith various sensors or devices installed on vehicle 402, such as device420. In one embodiment, device 420 is an RFID-enabled license plateinstalled on vehicle 402. Embodiments of an RFID-enabled license plateare described in U.S. Pat. Nos. 8,344,890 and 9,007,215, the disclosuresof which are incorporated by reference herein in their entirety.

In various embodiments, the disclosed OBD device 200 includes varioussecure features and implements various secure protocols. In someembodiments, unlike the conventional Bluetooth and Wi-Fi-based OBDsystems, the disclosed OBD device 200 does not require a networkconnection, or a data service, or pairing to another networked device tooperate. This independence from a network connection of the disclosedOBD device 200 can decrease the possibility of compromising the system200 as a result of a network connection. In various embodiments, OBDdevice 200 is configured to query OBD data from the OBD port without theability to access or make any changes to vehicle 402 parameters, or to“remotely control” any aspect of vehicle 402.

According to one exemplary embodiment, access to a memory of OBD device200 is only granted by using one or more authorized security keys. Theprovision of secure identification solutions is described in U.S. Pat.No. 7,081,819, U.S. Pat. No. 7,671,746, U.S. Pat. No. 8,237,568, U.S.Pat. No. 8,322,044, and U.S. Pat. No. 8,004,410, the disclosures ofwhich are incorporated by reference herein in their respective entirety.

As explained above, in some embodiments, OBD device 200 include two ormore wireless modules configured to interface with corresponding systemsat different frequencies, such as an UHF frequency and an NFC frequency.Multi-frequency RFID tags are described in Reissued U.S. Pat. Nos. RE43,355 and RE 44,691, the disclosures of which are incorporated byreference herein in their respective entirety.

In some embodiments, OBD device 200 can be configured to allow one ormore account management functions. Various account managementapplications for an RFID-enable license plate (or an “e-plate”) aredescribed in U.S. patent Ser. No. 14/459,299 and U.S. patent applicationSer. No. 14/459,299, the disclosures of which are incorporated herein byreference in their entirety.

The integration of one or more RFID transponders with an OBD devicecoupled onto the OBD port, in particular the inclusion of an UHF RFIDtransponder allows a wide range of useful applications to be builtaround the use of the OBD diagnostic data available at the OBD port. Forexample, in the rental car environment, traditional rental car returnprocess is manually operated, labour intensive, timing consuming, errorprone, and often resulting in poor customer experiences.

FIG. 5 illustrates a highly efficient rental car return process 500implemented based on communicating with a disclosed OBD device pluggedinto the OBD port of a rental vehicle in accordance with one embodimentdescribed herein.

As can be seen in FIG. 5, as vehicle 502 containing an embedded OBDdevice 504 enters a rental car return area, an UHF RFID reader 506installed roadside or in a gantry directly accesses the relevant data byquerying an UHF RFID transponder (not shown) within OBD device 504.Next, the query data, which can include fuel level, millage, and otherinformation necessary to determine a final rental cost, can be forwardedto and displayed on an employee's computer 508. The rental cost andother return information can be automatically finalized or finalizedwith a minimum amount of human intervention. This check-out informationcan be generated before the driver even parks the car. With theexception of possibly a visual inspection by the employee, the rentalreturn process can be completed before the driver even exits thevehicle.

In some embodiments, embedded OBD device 504 also includes a short rangeRFID transponder (not shown) which can allow the driver to verify andconfirm the check-out information and provide payment. For example, oncethe employee finishes and confirms the check-out data, the final paymentinformation can be sent to the driver's phone 510. The driver can viewthe payment information via an associated application, and alsointerface an NFC port of phone 510 with an NFC transponder of OBD device504 to receive and confirm the check-out information. Driver can thenprovide payment using the same application. Alternatively, if the driverhas an account set up with the rental company, the driver can use phone510 to confirm the final payment, verify the account has adequate funds,or charge up the account if the fund is inadequate.

Hence, compared to the traditional rental car return operations, the OBDdevice-based rental car return process 500 is a data driven, automatic,high reliable and accurate, and instantaneous process. Additionalbenefits of automatic process 500 can include cost reduction (as aresult of less devices and the elimination of receipt printing), no needto turn the vehicle on to check status on return, and obtaining instantECU diagnostics data to ensure vehicle is running properly. Automaticprocess 500 is likely to improve customer experience, which in turnwould allow more available resources to be used on customers and assets.Automatic process 500 based on using the disclosed OBD device can alsoallows the rental companies to use the vehicle data to drive loyalty,and to identify and reward more responsible and desirable customers(e.g. by offering responsible driver discounts).

Besides its applications in rental car business, the disclosed OBDdevice can also allow fleet management (e.g., for businesses operating alarge fleet of vehicles) to be made more efficient via the use of theembedded UHF RFID capability. In a similar manner to the rental carreturn process 500, vehicle data can be read from the OBD devices at adistance as drivers of the fleet enter or exit parking structures,and/or when they drive pass certain roadside locations where UHF RFIDreaders are installed.

The accompanying claims and their equivalents are intended to cover suchforms or modifications as would fall within the scope and spirit of theprotection. For example, the example apparatuses, methods, and systemsdisclosed herein can be applied wireless communication devicesincorporating HF and/or UHF RFID reader capabilities. The variouscomponents illustrated in the figures may be implemented as, forexample, but not limited to, software and/or firmware on a processor,ASIC/FPGA/DSP, or dedicated hardware. Also, the features and attributesof the specific example embodiments disclosed above may be combined indifferent ways to form additional embodiments, all of which fall withinthe scope of the present disclosure.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the steps of the various embodiments must be performed inthe order presented. As will be appreciated by one of skill in the artthe order of steps in the foregoing embodiments may be performed in anyorder. Words such as “thereafter,” “then,” “next,” etc. are not intendedto limit the order of the steps; these words are simply used to guidethe reader through the description of the methods. Further, anyreference to claim elements in the singular, for example, using thearticles “a,” “an” or “the” is not to be construed as limiting theelement to the singular.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with the aspectsdisclosed herein may be implemented or performed with a general purposeprocessor, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor maybe a microprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of receiver devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Alternatively, some steps ormethods may be performed by circuitry that is specific to a givenfunction.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored as one or moreinstructions or code on a non-transitory computer-readable storagemedium or non-transitory processor-readable storage medium. The steps ofa method or algorithm disclosed herein may be embodied inprocessor-executable instructions that may reside on a non-transitorycomputer-readable or processor-readable storage medium. Non-transitorycomputer-readable or processor-readable storage media may be any storagemedia that may be accessed by a computer or a processor. By way ofexample but not limitation, such non-transitory computer-readable orprocessor-readable storage media may include RAM, ROM, EEPROM, FLASHmemory, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that may be used tostore desired program code in the form of instructions or datastructures and that may be accessed by a computer. Disk and disc, asused herein, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above are also includedwithin the scope of non-transitory computer-readable andprocessor-readable media. Additionally, the operations of a method oralgorithm may reside as one or any combination or set of codes and/orinstructions on a non-transitory processor-readable storage mediumand/or computer-readable storage medium, which may be incorporated intoa computer program product.

Although the present disclosure provides certain example embodiments andapplications, other embodiments that are apparent to those of ordinaryskill in the art, including embodiments which do not provide all of thefeatures and advantages set forth herein, are also within the scope ofthis disclosure. Accordingly, the scope of the present disclosure isintended to be defined only by reference to the appended claims.

What is claimed is:
 1. An on-board diagnostic (OBD) device for avehicle, comprising: an OBD adapter configured to be plugged into an OBDport of a vehicle; and a first radio frequency identification (RFID)module electrically coupled to the OBD adapter and configured to:receive OBD data of a vehicle from an associated OBD port via the OBDadapter; and communicate at least a portion of the received OBD data toa first RFID reader when the first RFID module is queried by the firstRFID reader.
 2. The OBD device of claim 1, wherein the first RFID moduleis an ultra-high frequency (UHF) RFID module configured to communicatewith the first RFID reader using an UHF frequency band.
 3. The OBDdevice of claim 1, wherein the first RFID reader is installed at a firstlocation by the roadside, and wherein the first RFID module isconfigured to communicate with the first RFID reader when a vehiclecarrying the OBD device passes through the first location.
 4. The OBDdevice of claim 1, wherein the first RFID reader is installed at asecond location in a gantry above the ground, and wherein the first RFIDmodule is configured to communicate with the first RFID reader when avehicle carrying the OBD device passes under the second location.
 5. TheOBD device of claim 1, wherein the first RFID reader is a handheld RFIDreader.
 6. The OBD device of claim 1, wherein the OBD adapter isconfigured as a pass-through connector such that when the OBD adapter isplugged into an OBD port of a vehicle, the OBD adapter allows anotherODB device to access the OBD port without obstruction.
 7. The OBD deviceof claim 6, wherein the pass-through connector includes a pass-throughport that is substantially identical to the OBD port, so that when theOBD adapter is plugged into the OBD port, another ODB device cancontinue to access the OBD port by plugging into the pass-through port.8. The OBD device of claim 1, wherein the first RFID module isconfigured as a passive RFID module which functions without requiringpower from either a vehicle or the OBD device, whereby allowing thefirst RFID module to communicate with the first RFID reader when the OBDdevice is switched off or non-functional.
 9. The OBD device of claim 1,wherein the OBD device further comprises a second RFID moduleelectrically coupled to the OBD adapter and configured to: receive OBDdata of a vehicle from an associated OBD port via the OBD adapter; andcommunicate at least a portion of the received OBD data to a second RFIDreader when the second RFID module is queried by the second RFID reader.10. The OBD device of claim 9, wherein the second RFID module is a highfrequency (HF) RFID module configured to communicate with the secondRFID reader using a HF frequency band.
 11. The OBD device of claim 9,wherein the second RFID module is configured to communicate with anear-field communication (NFC)-enabled device by providing the at leasta portion of the received OBD data to the NFC-enabled device.
 12. TheOBD device of claim 9, wherein the second RFID module is one of aBluetooth™ module, a Wi-Fi module, and an NFC module.
 13. The OBD deviceof claim 9, wherein the second RFID module is configured as a passiveRFID module which functions without requiring power from either avehicle or the OBD device, whereby allowing the second RFID module tocommunicate with the second RFID reader when the OBD device is switchedoff or non-functional.
 14. The OBD device of claim 1, wherein the OBDdevice further comprises a microprocessor coupled between the OBDadapter and the first RFID module and configured to process the receivedOBD data via the OBD adapter.
 15. The OBD device of claim 14, whereinthe microprocessor is coupled to the first RFID module through an I²Ccontrol bus.
 16. The OBD device of claim 1, wherein the first RFIDmodules is further configured to communicate with an RFID-enabledlicense plate installed on the vehicle.
 17. The OBD device of claim 1,wherein the receive OBD data include one or more of: vehicle's VINnumber, mileage, fuel level, tire pressure monitoring system (TPMS)threshold, and a set of diagnostic trouble codes.
 18. The OBD device ofclaim 1, wherein the OBD device is configured to operate withoutrequiring a network connection, a data service, or a pairing to anothernetworked device.
 19. A method for providing OBD data of a vehicle to anRFID reader, comprising: receiving a query for OBD data from an RFIDreader; receiving, by an UHF RFID module electrically coupled to an OBDport of the vehicle, current OBD data of the vehicle; and transmitting,from the UHF RFID module, the current OBD data to the RFID reader. 20.The method claim 19, wherein the RFID reader is installed at a firstlocation by the roadside, and wherein the UHF RFID module transmits thecurrent OBD data to the RFID reader when the vehicle passes through thefirst location.
 21. The method claim 19, wherein the RFID reader isinstalled at a second location in a gantry above the ground, and whereinthe UHF RFID module transmits the current OBD data to the RFID readerwhen the vehicle passes under the second location.
 22. A method forproviding OBD data of a vehicle to an RFID reader, comprising: querying,from an OBD port of the vehicle, OBD data of the vehicle using an OBDadapter of an OBD device coupled with the OBD port; storing at least aportion of the received OBD data into a memory of the OBD device; andreceiving a query from an RFID reader for the OBD data of the vehicle;and transmitting at least a portion of the stored OBD data to the RFIDreader using an RFID module of the OBD device.
 23. The method claim 22,wherein querying the OBD data and storing the at least a portion of thereceived OBD data into the memory of the OBD device are performedperiodically at a predetermined time interval.